Skip to main content
Feedback

Properties panel, Advanced tab

The Properties panel Advanced tab can be used to set additional properties that modify the configuration of a basic runtime, runtime cluster, or private runtime cloud.

Account Working Data Directories

  • Default Value: See details in linked topic
  • Format: See details in linked topic
  • com.boomi.container.accountsDirs

See the topic about working data storage.

Allow Browsing

  • Default Value: Off for runtime clouds. On for basic runtimes and runtime clusters
  • Format: Check box
  • com.boomi.container.disableConnectorBrowsing

If selected, connector operations can use this runtime to browse and import objects.

When used with a private runtime cloud, this property works in conjunction with the Allow Browsing property that is set on the Cloud Properties tab:

  • If SELECTED on the Cloud Properties tab and SELECTED in the Cloud Properties dialog — Browsing is enabled for everyone.
  • If SELECTED on the Cloud Properties tab and CLEARED in the Cloud Properties dialog — Browsing is enabled for the runtime cloud owner but is disabled for Cloud tenants. Tenants see the runtime cloud in the list but when they attempt to browse they receive an error.
  • If CLEARED on the Cloud Properties tab and CLEARED in the Cloud Properties dialog — Browsing is disabled.
  • If CLEARED on the Cloud Properties tab and SELECTED in the Cloud Properties dialog — Browsing is disabled.

Allow User Logs

  • Default Value: Off for runtime clouds. On for basic runtimes and runtime clusters.
  • Format: Check box
  • com.boomi.container.disableUserLogs

Used to enable or disable the user log feature in a process. When you select this check box, user logs are enabled.

Approve Listener Bypass

  • Default Value: Not set
  • Format: Comma-separated list of connector types
  • com.boomi.container.listen.worker.connectors

Some listeners run on the main JVM on the runtime cloud so they cannot utilize concurrent executions when running in low latency mode. To bypass listeners running in clouds and in the execution worker, add the custom container property com.boomi.container.listen.worker.connectors and set the property value to a comma-separated list of connector types. The only connector types allowed are sfpe and azuresb.

Important

This property should only be applied to local clouds.

Archive Processed Documents

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.account.archive.data

If selected, processed document archiving is enabled for the private runtime cloud or local runtime.

Async Message Poller Timeout for Cluster Scale Down

  • Default Value: 10 minutes
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.elasticity.asyncPollerTimeout

The amount of time to wait before assuming that a step within a node's shutdown process has failed when it takes too long to complete or encounters a timeout issue. In the event that a step has failed, the shutdown is aborted and the offending node is rolled back to a functional state. If the user does not manually set this property value, the container assumes a default value of 600,000 milliseconds (10 minutes).

Important

The Async Message Poller Timeout for Cluster Scale Down property value needs to be larger than the value set in the Force Restart Override for Cluster Scale Down property.

Runtime Data Directory Level

  • Default Value: 0
  • Format: 0, 1, 2, 3 or 4
  • com.boomi.container.dataDirNestLevel

See the topic about the Atom’s data directory structure.

Runtime Pending Shutdown Delay

  • Default Value: 0
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.pendingShutdownWarnTime

The amount of time the runtime should pause before shutting down to accommodate load balancers. See the topic about Runtime status monitoring.

Execution Worker Idle Timeout

  • Default Value: 86,400,000 (= 24 hours)
  • Format: Milliseconds
  • com.boomi.container.worker.idleTimeout

The amount of time before an idle execution worker will automatically shut down.

Execution Worker Local Port Range

  • Default Value: 20000 - 30000
  • Format: Range of port numbers
  • com.boomi.container.worker.portRange

The range of local ports on which execution workers can listen for connections from runtime cloud nodes.

Execution Worker Pending Updates Queue Size

  • Default Value: Not set
  • Format: Positive Integer
  • com.boomi.container.worker.maxPendingUpdates

The number of elements that are passed through the execution worker's pending updates queue at one time. Increase this number if you experience slowness when updating extensions. Conversely, setting too large of a number may cause memory issues. If the user does not manually set this property value, the runtime assumes a default value of 100.

note

This property is relevant only to Clouds that have allocated workers.

Execution Worker Startup Timeout

  • Default Value: 120000 (=2 minutes)
  • Format: Milliseconds
  • com.boomi.container.worker.startupTimeout

The amount of time that the system will wait for an execution worker to start successfully.

Execution Worker Thread Pool Idle Timeout

  • Default Value: 150,000 (= 5 minutes)
  • Format: Milliseconds
  • com.boomi.container.worker.threadPool.idleTimeout

The amount of time before an idle execution thread in an execution worker will be stopped.

Execution Worker Time To Live

  • Default Value: 86,400,000 (= 24 hours)
  • Format: Milliseconds
  • com.boomi.container.worker.ttl

The amount of time after which an execution worker will automatically shut down.

note

If the load on active execution workers drops, the runtime cloud reduces the number of execution workers to the Minimum Execution workers value. In that case, it is possible for an execution worker to shut down before its Execution worker Time to Live value is reached.

Execution Worker Heartbeat Timeout

  • Default Value: 300,000 ms (= 5 mins)
  • Format: Milliseconds
  • com.boomi.container.worker.heartbeatTimeout

The amount of time in milliseconds before an unresponsive execution worker is marked as inactive. The default value is 300,000 ms. Requires a runtime restart to enable.

Execution Workers Enabled

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.worker.enabled

See the topic about enabling execution workers.

Auto Restart on Out Of Memory

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.resource.restartOnOutOfMemoryError

Specifies whether the runtime should attempt to restart when it encounters an Out Of Memory error.

Auto Restart on Too Many Files Error

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.restartOnTooManyOpenFilesError

(Linux only) Specifies whether the runtime should attempt to restart when it encounters a Too Many Open Files error.

Bouncy Castle Library Version

  • Default Value: 1.45
  • Format: 1.45 or LATEST
  • com.boomi.container.bouncyCastleVersion

Specifies which version of the Bouncy Castle library the runtime uses.

Important

Runtimes executing processes using the OFTP2 Client connector or OFTP2 Server connector should be configured with Bouncy Castle Library Version set to LATEST.

Clean Up Custom Script Engine Data on Completion

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.resetScriptEngineData

If set to true (the default), this property causes the immediate cleanup of leftover data after custom script execution.

Client Default Connect Timeout

  • Default Value: 120000
  • Format: Milliseconds
  • -Dsun.net.client.defaultConnectTimeout

The amount of time that the runtime should spend trying to establish an HTTP client connection.Increase this value if the HTTP endpoints are known to take longer than two minutes to return a response.

Client Default Read Timeout

  • Default Value: 120000
  • Format: Milliseconds
  • -Dsun.net.client.defaultReadTimeout

The amount of time that the runtime should spend attempting to read data from an established HTTP client connection. Increase this value if the HTTP endpoints are known to take longer than two minutes to return a response.

Cloud Partition Replicas

  • Default Value: 3
  • Format: Positive integer
  • com.boomi.container.cluster.numberOfReplicas

A tuning option for the Cloud Partition Size property. This option helps to randomize the node selection.

Cloud Partition Size

  • Default Value: -1 (special value for using all nodes in a cluster)
  • Format: Positive integer
  • com.boomi.container.cluster.partitionSize

Determines how many nodes are used for executions for a given account.In order for the Account Concurrent Execution Limit to take effect, the Cloud Partition Size property must also be set and then the runtime cloud must be restarted. The Account Concurrent Execution Limit is set in the Attachment Quotas tab.

Cluster Bootstrap Timeout

  • Default Value: 60,000 (= 60 seconds)
  • Format: Milliseconds
  • com.boomi.container.cloudlet.initStateTimeout

The amount of time that the clustering protocol should spend trying to find other nodes.

Cluster Network Bind Address

  • Default Value: Blank (local machine address)
  • Format: A different address
  • com.boomi.container.cloudlet.bindAddress

If you have multiple network addresses, you can specify the address on which you want to listen.

Cluster Network Transport Type

  • Default Value: MULTICAST
  • Format: MULTICAST or UNICAST
  • com.boomi.container.cloudlet.clusterConfig

Specifies the cluster's transmission protocol. Newly installed Docker runtime clusters and Docker Clouds are explicilty set to UNICAST in the Advanced Tab of the Properties Panel; clearing the UNICAST value defaults the Cluster Network Transport Type property automatically to MULTICAST unless specified otherwise. See the topic about setting up unicast support.

Cluster Problem Automatic Delete Delay

  • Default Value: 0
  • Format: Milliseconds
  • com.boomi.container.cloudlet.elasticity.cluster.problem.nodeCleanupTimeout

See the topic about cluster monitoring. If a value is not manually specified in the property field, the property automatically assumes a default of 0 milliseconds.

Cluster Problem Automatic Shutdown Delay

  • Default Value: 600000 (10 minutes)
  • Format: Milliseconds
  • com.boomi.container.cloudlet.problemShutdownTime

See the topic about cluster monitoring. If not set, the runtime assumes a default of 600,000 milliseconds (10 minutes).

Cluster Rolling Restart Percentage

  • Default Value: 50
  • Format: A percentage represented by a whole number from 0 to 100
  • com.boomi.container. cluster.rollingRestart.clusterRestartPercentage

The percentage of nodes in a cluster that will restart simultaneously as part of a rolling restart. If you set this property to 0, the cluster restarts one node at a time. If you set it to 100, the entire cluster except for the head node begins to restart simultaneously. The head node waits for the other nodes to complete the restart process.

Compress History after x Days

  • Default Value: 2
  • Format: Days represented by a whole number
  • com.boomi.container.compressDays

The number of days after which logs, processed documents, and temporary data will be automatically compressed on disk.

note

The compress activity is disabled by setting a value greater than the runtime's purge. You can also increase the value of the Purge Manager Thread property, if resources are available, to avoid compression issues with your runtime.

Connector Browsing Idle Timeout

  • Default Value: 900000 (15 minutes)
  • Format: Milliseconds
  • com.boomi.container.browser.idleTimeout

The amount of time before an idle execution worker that is allocated to perform connector browsing will automatically shut down.

Connector Browsing Maximum Browse Time

  • Default Value: 15 minutes
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.browser.maxBrowseTime

The maximum amount of time that you want to allow an execution worker's browse operation to take.

Connector Browsing Max Thread Count

  • Default Value: 50
  • Format: Positive integer
  • com.boomi.container.browser.maxBrowseCount

The maximum number of threads that are allocated to an execution worker for browsing.

Connector Browsing Time to Live

  • Default Value: 3600000 (60 minutes)
  • Format: Milliseconds
  • com.boomi.container.browser.ttl

The amount of time before an execution worker that is allocated to perform connector browsing will automatically shut down.

Connector Server Startup Timeout

  • Default Value: 15 minutes
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.connectorServer.startupTimeout

The amount of time a listener is allowed for initialization. For listener processes, initializing the listener is part of the deployment process. While initialization is pending, the runtime is prevented from executing other actions. Failure to initialize a listener before timeout occurs results in a deployed but offline listener, just as it does in the case of any other exception — for example, a class not found error.

Connector Trace Logging

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.connector.trace

Used to troubleshoot connectors.

Control ID Cache Idle Timeout

  • Default Value: 10
  • Format: Seconds
  • com.boomi.container.controlid.idleTimeoutSec

The amount of time the control ID cache can be idle before it times out. Setting this property can improve the performance of incoming EDI document handling in a runtime running in a multi-node runtime cloud. The maximum is 300 seconds.

Control ID Cache Time to Live

  • Default Value: 60
  • Format: Seconds
  • com.boomi.container.controlid.ttlTimeoutSec

The amount of time to live of the control ID cache. Setting this property can improve the performance of incoming EDI document handling in a runtime running in a multi-node runtime cloud. The maximum is 300 seconds.

Customized Procrunner Script File Name

  • Default Value: Not set
  • Format: See details in linked topic
  • com.boomi.container.script.type.procrunner

See the topic about customized script files.

Customized Procbrowser Script File Name

  • Default Value: Not set
  • Format: See details in linked topic
  • com.boomi.container.script.type.procbrowser

See the topic about customized script files.

Customized Procworker Script File Name

  • Default Value: Not set
  • Format: See details in linked topic
  • com.boomi.container.script.type.procworker

See the topic about customized script files.

Customized Restart Script File Name

  • Default Value: Not set
  • Format: See details in linked topic
  • com.boomi.container.script.type.restart

See the topic about customized script files.

Debug Log Level Threshold

  • Default Value: DEBUG
  • Format: DEBUG, INFO, OFF, SEVERE, WARNING
  • com.boomi.container.debugThreshold

See the topic about logging debug messages.

Decommission Time for Post Pause Sleep

  • Default Value: Not set
  • Format: Minutes
  • com.boomi.container.decommission.time.post.pause.sleep

See the topic about cluster monitoring. If a value is not manually specified in the property field, the property automatically assumes a default of two minutes.

Disk Space Monitoring

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.config.runDiskspaceMonitor

See the topic about disk space monitoring. The property is enabled by default. The monitoring system runs based on the value that is set in the Disk Space Monitoring Frequency property.

Disk Space Monitoring Account Auto Suspension

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.config.diskspacemonitor.enableAccountAutoSuspension

Determines whether an account is automatically suspended when it exceeds its disk space allotment. By default, this property is enabled.

Disk Space Monitoring Frequency

  • Default Value: 3600000 (60 minutes)
  • Format: Milliseconds
  • com.boomi.container.config.diskspaceMonitorInterval

See the topic about disk space monitoring.

Disk Space Monitoring Threads

  • Default Value: Varies
  • Format: Positive integer
  • com.boomi.container.config.diskspacemonitor.numThreads

The number of threads to be used for monitoring disk space. If Disk Space Monitor is run from a runtime, the default is 1. If the Disk Space Monitor is run from the Runtime Maintenance Server, the default is 10.

For more information, see the topic about Disk space monitoring. |

Disk Space Monitoring Verbose Logging

  • Default Value Off
  • Format: Check box
  • com.boomi.container.config.diskspacemonitor.verboseLogging

See the topic about disk space monitoring.

Disk Space Warning Limit

  • Default Value: Not set
  • Format: A percentage represented by a whole number from 0 to 100
  • com.boomi.container.config.diskspaceMonitorWarnThreshold

To help you monitor disk space usage, this property logs a warning message every time the threshold is met or exceeded. For more information, see the topic about disk space monitoring.

DNS Time to Live

  • Default Value: 30
  • Format: Seconds
  • -Dsun.net.inetaddr.ttl

The amount of time that successful DNS lookups should be cached. Decrease this value if you call external hosts that experience frequent IP address changes to their DNS hostname. Entering a value of -1 seconds enables continuous caching, and entering a value of 0 seconds disables caching.

Dump to File When Exceeding Open File Threshold

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.resource.dumpToFileOnLowOpenFiles

(Linux only) Specifies whether the runtime should generate a file dump when either of the following occurs:

  • A Too Many Open Files error occurs.
  • The Low Remaining Open Files Threshold value is exceeded.

Early Stale Worker TTL Percentage

  • Default Value: Not set
  • Format: Percentage
  • com.boomi.container.worker.ttl.fudge.factor.percentage

The Early Stale Worker TTL Percentage property is a percentage of the time value set in the Execution worker Time To Live property. When Early Stale Worker TTL Percentage is set, an execution worker is eligible for early shut down and replacement when it reaches the specified time percentage. As a result, this property staggers execution worker restarts to improve runtime cloud performance.

For example, say that you have Execution worker Time to Live property set to 24 hours, and the Early Stale Worker TTL Percentage property set to 50%. This means that the execution worker may shut down and get replaced after it passes the 12 hour mark, without needing to fulfill the entire 24 hour setting in the Execution worker Time to Live property.

If not set explicitly in the user interface, this property assumes a default value of 50%.

Enable Debug Logging

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.debug

This property works in conjunction with the Enable Trace Logging property. See the topic about enabling debug and trace logging in a runtime. This property should be used only as directed by the Support team.

Enable Jgroups Debug Logging

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.jgroupsLogging

If selected, detailed Jgroups communication information among the nodes in a runtime cluster or runtime cloud is logged.

Enable Milliseconds Logging

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.millisecondsLogging

This property enables container and process logging in milliseconds. If enabled, the timestamp is displayed in MMM d, yyyy h:mm:ss.SSS format. If disabled (default), the timestamp is displayed in MMM d, yyyy h:mm:ss format.

Enable Persisted Connector Cache

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.connector.persistence.enabled

If selected, the Connector Listen framework is allowed to use the Persisted Connector Cache to save and retrieve the replayID on send and receive actions. This allows connectors to persist the replayID and start over from the point before the stop when pausing or stopping the listener.

If the persisted replayID is invalid, the fail over is to the initial replayID mentioned in the connection.

Enable SSL Debug Logging

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.debug.ssl

See the topic about enabling verbose SSL logging in a runtime. This property should be used only as directed by the Support team.

note

This container property has an equivalent system property called -Djavax.net.debug that can be set in <installation_directory>/bin/atom.vmoptions. As a rule, the container property takes precedence. If the system property exists in /bin/atom.vmoptions, the equivalent container property will be stored in <installation_directory>/conf/container.properties when you click Save on the Properties panel. The original system property will be removed from /bin/atom.vmoptions.

Enable Standard Output and Error Logging

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.logging.std.enabled

Enables the standard output (stdout) and standard error (stderr) logging functionality in addition to the container log. For Docker containers, this property is enabled by default. Set the Standard Error Log Level property to determine which logs are included in stderr.

Enable Trace Logging

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.trace

This property works in conjunction with the Enable Debug Logging property. See the topic about enabling debug and trace logging in a runtime. This property should be used only as directed by the Support team.

Enable XML External Entity Processing

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.xml.enableExternalEntities

Specifies whether external XML entity references will be processed when parsing XML documents. This can be a security vulnerability and therefore it is disabled (set to FALSE) by default.

Encrypted Proxy Password

  • Default Value: If the password exists, SET_AND_ENCRYPTED appears
  • Format: Add or delete
  • com.boomi.container.proxyPassword.encrypted

This property appears in the list if an encrypted proxy password exists on the runtime. You can delete this password by deleting the property, but you cannot edit the password. If you mistakenly delete the property, you can re-add it.

Endorsed Directories

  • Default Value: <java-home>/lib/endorsed
  • Format: String
  • -Djava.endorsed.dirs

Identifies one or more directories to be searched for JAR files that implement Java Endorsed Standards.

note

This property is not applicable for containers that run on Java version 11 and should not be used unless the runtime runs on Java 8.

Execute Processes as Forked JVMs

  • Default Value: MULTI_THREAD
  • Format: MULTI_PROCESS (enables forked execution) or MULTI_THREAD (disables forked execution), ELASTIC (enables forked executions to run in individual Kubernetes pods)
  • com.boomi.container.processExecMode

Used to enable or disable forked execution in a runtime cluster.

Important

Forked execution (MULTI_PROCESS) is the only supported execution mode in runtime clouds. As such, do not select the MULTI_THREAD option for a runtime cloud.

External Hostname

  • Default Value: localhost
  • Format: String
  • com.boomi.container.external.hostname

Used by the mail connector to populate a header when sending to the mail server.

Force Restart Override for Cluster Scale Down

  • Default Value: 10 minutes
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.elasticity.forceRestartOverride`

The amount of time to wait for processes to finish running on the node before the node is stopped. If the user does not manually set this property value, the runtime assumes a default value of 600,000 milliseconds (10 minutes). If a process execution is aborted as a result of this configuration, the documents associated with the process are maintained in a shared file system and therefore can be manually re-executed from another node.

Important

The Async Message Poller Timeout for Cluster Scale Down property value needs to be larger than that of the Force Restart Override for Cluster Scale Down property.

Force Start Shared Web Server

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.plugin.force.start.shared_http_server

Always starts the Shared Web Server even when no listeners are deployed.

Generate Heap Dump on Low Memory

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.resource.heapDumpOnLowMemory

Specifies whether the runtime should automatically generate a heap dump when it enters low memory status. See the topic about performance troubleshooting.

Headless Mode

  • Default Value Off
  • Format: Check box
  • -Djava.awt.headless

Specifies whether the basic runtime, runtime cluster, or runtime cloud should run in Java headless mode.

Heap Dump on Out of Memory Error

  • Default Value: OfF
  • Format: Check box
  • -XX:+HeapDumpOnOutOfMemoryError

Specifies whether the runtime should automatically generate a heap dump when it encounters an Out Of Memory error. See the topic about high-volume troubleshooting. This property should be used only as directed by the Support team.

HTTPS Protocols

  • Default Value: Not set
  • Format: String containing one or more Transport Layer Security protocols separated by commas: TLSv1,TLSv1.2.
  • com.boomi.container.httpsProtocols

This is the Java system property https.protocols, which specifies the enabled Transport Layer Security (TLS) protocol(s) for HTTPS connections via the HTTP Client connector and other connectors that run HTTP clients for connecting to services. Java 8 enables TLSv1 and TLSv1.2 by default.

Initial Hosts for Unicast

  • Default Value: Not set
  • Format: String
  • com.boomi.container.cloudlet.initialHosts

Identify one or more specific host machines as initial hosts when using unicast for cluster communication. See the topic about setting up unicast support.

Java Class Path

  • Default Value: Not set
  • Format: String
  • -classpath

Identifies one or more directories to be searched for classes and other resource files.

Java Class Path Prepend

  • Default Value: Not set
  • Format: String
  • -classpath/p

Identifies one or more directories to be added to the beginning of the Java Class Path list.

Java Library Path

  • Default Value: Not set
  • Format: String
  • -Djava.library.path

Identifies one or more directories to be searched for native libraries.

Java Security Compatibility

  • Default Value: 2016.01
  • Format: String
  • -Dcom.boomi.container.securityCompatibility`

See the topic about controlling Java security compatibility.

JGroups Clustered Library Version

  • Default Value: 3
  • Format: Integer
  • -Dcom.boomi.container.clusterLibVersion

The version of JGroups to be used for clustered basic runtimes (basic runtimes that are used in runtime clusters and runtime clouds). See the topic about upgrading clustered basic runtimes to JGroups 3.

JMX Remote Authentication

  • Default Value: Off
  • Format: Check box
  • -Dcom.sun.management.jmxremote.authenticate

See the topic about enabling remote JMX on a basic runtime.

JMX Remote Port

  • Default Value: 5002
  • Format: Integer
  • -Dcom.sun.management.jmxremote.port

See the topic about enabling remote JMX on a basic runtime.

JMX Remote RMI Port

  • Default Value: 5002
  • Format: Integer
  • -Dcom.sun.management.jmxremote.rmi.port`

See the topic about enabling remote JMX on a basic runtime.

JMX Remote SSL

  • Default Value: Off
  • Format: Check box
  • -Dcom.sun.management.jmxremote.ssl`

See the topic about enabling remote JMX on a basic runtime.

Listener Startup Mode

  • Default Value:
    • Single-tenant: ALL
    • Multi-tenant and running as single specific account: NONE
    • Multi-tenant: MULTITENANT_ONLY
    • Secure Listen enabled: EFFECTIVE_SINGLE_TENANT_ONLY
    • Secure Listen disabled: NONE
  • Format: ALL, MULTITENANT_ONLY, NONE, EFFECTIVE_SINGLE_TENANT_ONLY
  • com.boomi.container.startListeners

Defines how listeners are started. Only runtime cloud owners can set this property.

Important

Boomi recommends that you do not set a value for this property. The runtime determines the appropriate mode for each container (main JVM, execution workers, etc.) and by setting a value, the intended behavior is overridden and every JVM uses the same mode. As a result, listeners may not run where expected. This property can be set to NONE if listeners should not be started in the runtime. You can view the status of listeners on the Listeners panel. In that panel you can also pause, resume, and restart listeners. Secure Listen:

  • When a value is not set for this property (the ideal configuration), the main JVM operates in multi-tenant mode and execution workers are single tenant. This allows any supported connector having a Listen operation (Web Services Server, Microsoft Azure Service Bus, Salesforce Platform Events, etc.) to operate as multi-tenant and the listener to run in the runtime cloud node's main JVM. Additionally, single-tenant connectors only run on execution workers.
  • When set to EFFECTIVE_SINGLE_TENANT_ONLY (not recommended), the main JVM and any execution workers operate as single tenant.

Logger Queue Size

  • Default Value: Not set
  • Format: Positive Integer
  • com.boomi.container.logging.queueSize

The number of buffered log statements held in memory before writing to log files. You can increase the size of the logging queue to allow a larger number of log statements. Coordinate this property with the Logger Timeout property to tune logging throughput. For more information, see Boomi Community article.

Logger Timeout

  • Default Value: Not set
  • Format: Milliseconds
  • com.boomi.container.logging.timeOut

The timeout period for log messages to be added to the logging queue. If the initial attempt fails, the log handler attempts to add the log after the timeout period. If the second attempt fails, the log handler discards the message. Coordinate this property with the Logger Queue Size property to tune logging throughput. For more information, see Boomi Community article.

Low Latency Warning Threshold

  • Default Value: -1 (disabled)
  • Format: Milliseconds
  • com.boomi.container.account.lowLatency.processElapsedWarnThreshold

The amount of time after which an otherwise successful low latency process is flagged as a "warning". If you set it to a value less than or equal to zero, the warning is disabled. You do not need to restart the runtime after setting this property if you change it through the Properties dialog. If this value exists in the account.properties file, then it is used. If the value does not exist in the account.properties file or if the account.properties file does not exist, then this value is read from the container.properties file.

Low Memory Mode Threshold

  • Default Value: Calculated between 60-100%, depending on existing heap memory usage.
  • Format: A percentage represented by a whole number from 0 to 100
  • com.boomi.container.resource.lowMemoryThreshold

Setting the value to 100 disables the Low memory mode feature. The percentage of JVM memory usage before a node goes into "low memory" execution mode.

Low Open Files Threshold

  • Default Value: 90
  • Format: A percentage represented by a whole number from 0 to 100
  • com.boomi.container.lowOpenFilesThreshold

(Linux only) If the open file count is being monitored, the percentage of the maximum number allowed by the system that should cause a runtime to respond. The Monitor Number of Open Files property controls open file monitoring. By default, monitoring is enabled for runtime clouds and disabled for basic runtimes and runtime clusters. The runtime responds based on the Auto Restart on Too Many Files Error and Dump to File When Exceeding Open File Threshold settings.

Mapping Expand Child Elements Legacy

  • Default Value: Off
  • Format: Check box
  • com.boomi.container.mapping.expandChildElementsLegacy

If selected, mapping behavior with regard to the presence of instance identifiers in a destination profile persists as it was prior to the May 2021 release. This behavior erroneously results in the creation of duplicate child elements in some cases.

note

Support for this property was discontinued in the summer of 2021. Selecting this property should therefore be regarded solely as a means to enable processes that rely on the legacy behavior to remain usable for a short time. These processes should be updated to rely on the corrected behavior as soon as possible. Once a process is updated and redeployed, this property should be deselected or removed.

Maximum Cached Control IDs

  • Default Value: 10
  • Format: Integer
  • com.boomi.container.controlid.maxids

The maximum number of control IDs that are cached. Setting this property can improve the performance of incoming EDI document handling in a runtime running in a multi-node runtime cloud. If the value is set higher than 50, a maximum of 50 control IDs are cached.

Maximum Cached Transaction Keys

  • Default Value: 10
  • Format: Integer
  • com.boomi.container.controlid.maxTransactions

The maximum number of transaction keys that are cached in a runtime cloud. This property applies only to multi-node runtime clouds for node-to-node communication. Setting this property for a runtime cloud can improve the performance of incoming EDI document handling in the cloud’s attached basic runtimes. If the value is set higher than 50, a maximum of 50 transaction keys are cached.

Maximum Document Elements Cache Size

  • Default Value: 10,000
  • Format: Integer
  • com.boomi.container.transform.maxCacheSize

The maximum number of document elements to keep in memory per parsed document when low memory mode has been triggered.

Maximum Execution Threads per Forked Execution

  • Default Value: 50
  • Format: Integer
  • com.boomi.container.forker.maxUserThreads

The maximum number of threads that can run in a forked JVM.

Maximum Execution Threads per Execution Worker

  • Default Value: 100
  • Format: Integer
  • com.boomi.container.worker.maxUserThreads

The maximum number of threads that can run in an execution worker JVM.

Maximum Execution Threads per Connector Browser

  • Default Value: 100
  • Format: Integer
  • com.boomi.container.browser.maxUserThreads

The maximum number of threads that can run in a Connector Browser JVM.

Maximum Flow Control Units

  • Default Value: 10
  • Format: Integer
  • com.boomi.container.flowControl.maxUnitCount

The maximum number of flow control units. This value takes precedence over the Flow Control step’s configuration.

Maximum Forked Execution Time in Cloud

  • Default Value: Not set
  • Format: Milliseconds
  • com.boomi.container.maxExecutionTime

The maximum amount of time that you want to allow a forked execution process to run.

Maximum Number of Active Batches per Listener

  • Default Value: 5
  • Format: Integer
  • com.boomi.container.connector.sdkListener.maxBatchLimit

The maximum number of listener batches that a listener instance is allowed to create for SDK connectors with listeners.

note

When set to 0, the Listener does not create batches. Boomi recommends entering a positive integer.

Maximum Queued Executions per Node

  • Default Value: 200
  • Format: Integer
  • com.boomi.container.maxQueuedExecutions

The maximum number of queued executions that can wait to run on a given node. This property can be used

  • by basic runtimes and by runtime clusters that do not have forked execution enabled
  • if the Maximum Simultaneous Executions per Node property is enabled

Maximum Queued Forked Executions per Node

  • Default Value: 200
  • Format: Integer
  • com.boomi.container.forker.maxQueuedForkedExecutions

The maximum number of queued forked executions that can wait to run on a given node. This property can be used by runtime clouds and by runtime clusters that have forked execution enabled.

Maximum Simultaneous Executions per Node

  • Default Value: Unlimited
  • Format: Integer
  • com.boomi.container.maxRunningExecutions

The maximum number of simultaneous execution JVMs that can run on a given node. This property can be used by basic runtimes and by runtime clusters that do not have forked execution enabled. If this property is set, a queue is enabled for pending executions that exceed the maximum limit for running executions. Use the Maximum Queued Executions per Node and Timeout for Queued Executions per Node properties to set the queue size and time limit. If this property is not set, queuing is not enabled and the number of concurrent executions per node is unlimited.

Maximum Simultaneous Forked Executions per Node

  • Default Value: 50
  • Format: Integer
  • com.boomi.container.forker.maxRunningForkedExecutions

The maximum number of simultaneous forked execution JVMs that can run on a given node. This property can be used by runtime clouds and by runtime clusters that have forked execution enabled.

Maximum Simultaneous Forked JVMs per Node

  • Default Value: -1
  • Format: Integer
  • com.boomi.container.forker.maxRunningForkedJVMs

The maximum number of the sum of forked executions, execution workers, and forked browse sessions that can run on a given node. Forked executions view this value as a hard limit, preventing any additional forked executions from being created on the node. Execution workers and forked browse sessions view this value as a soft limit so execution workers can still be scheduled on the node. The default value, -1, is unlimited. This property can be used by runtime clouds and runtime clusters that have forked executions enabled.

Maximum Size for Update Operation

  • Default Value: 1,048,576 bytes
  • Format: Integer
  • com.boomi.container.connector.sizeLimitedUpdateOperation.maxSize

The maximum size allowed for input documents in bytes. A value of -1 overrides filtering based on size, allowing any size document to go through.

Minimum Number of Hosts for Unicast Auto-detect

  • Default Value: 2
  • Format: Integer
  • com.boomi.container.cloudlet.minInitialHosts

The minimum number of initial hosts to search for when using unicast for cluster communication. See the topic about setting up unicast support.

Monitor Number of Open Files

  • Default Value: TRUE for runtime clouds. FALSE for basic runtimes and runtime clusters.
  • Format: TRUE or FALSE
  • com.boomi.container.resource.monitorOpenFiles

(Linux only) Specifies whether the runtime should monitor the open file count and compare it to the maximum number allowed by the system. Open files include both files that are open for read/write activity and open network connections. By default, monitoring is enabled for runtime clouds and disabled for basic runtimes and runtime clusters.

note

For forked executions in a runtime cluster or runtime cloud where monitoring is enabled, the primary JVM that manages forked executions will be monitored. However, monitoring is always disabled for the JVMs that are running individual processes.

Multicast Address

  • Default Value: 228.10.10.10
  • Format: A different address
  • com.boomi.container.cloudlet.mcastAddress

ee the topic about changing the multicast address.

Multicast Port

  • Default Value: 45588
  • Format: A different port
  • com.boomi.container.cloudlet.mcastPort

See the topic about changing the multicast port.

Non Proxy Hosts

  • Default Value: Not set
  • Format: String
  • com.boomi.container.nonProxyHosts

Identifies hosts that should be connected to directly, bypassing the configured HTTP proxy. The value can be a list of hosts, each separated by a pipe (|). An asterisk (*) can be used for matching. For example, *.mycompany.com\|localhost would indicate that any hosts suffixed by mycompany.com or a host of localhost should not go through the proxy.

note

This container property has an equivalent system property called -Dhttp.nonProxyHosts that can be set in <installation_directory>/bin/atom.vmoptions. As a rule, the container property takes precedence. If the system property exists in /bin/atom.vmoptions, the equivalent container property will be stored in <installation_directory>/conf/container.properties when you click Save on the Properties panel. The original system property will be removed from /bin/atom.vmoptions.

Orchestrated Container

  • Default Value: Not set
  • Format: Check box
  • com.boomi.container.cloudlet.problemShutdownTime

See the topic about cluster monitoring.

Prefer IPv4Stack

  • Default Value: Off
  • Format: Check box
  • -Djava.net.preferIPv4Stack

Specifies whether the runtime cluster node or runtime cloud cluster should use IPv4 for networking. has been tested with IPv4. Therefore, strongly recommends turning this property on.

Process Execution Directory Level

  • Default Value: 0
  • Format: 0, 1, 2, 3 or 4
  • com.boomi.container.executionDirNestLevel

See the topic about the process execution directory structure.

Processed Document Archive Directory

  • Default Value: Not set
  • Format: Full directory path
  • com.boomi.container.archiveDir

The directory to which processed documents are archived if processed document archiving is enabled.

Proxy Host

  • Default Value: Not set
  • Format: String
  • com.boomi.container.proxyHost

The host name of the HTTP proxy server.

note

This container property has an equivalent system property called -Dhttp.proxyHost that can be set in <installation_directory>/bin/atom.vmoptions. As a rule, the container property takes precedence. If the system property exists in /bin/atom.vmoptions, the equivalent container property will be stored in <installation_directory>/conf/container.properties when you click Save on the Properties panel. The original system property will be removed from /bin/atom.vmoptions.

Proxy Port

  • Default Value: 80
  • Format: Integer
  • com.boomi.container.proxyPort

The port number of the HTTP proxy server.

note

This container property has an equivalent system property called -Dhttp.proxyHost that can be set in <installation_directory>/bin/atom.vmoptions. As a rule, the container property takes precedence. If the system property exists in /bin/atom.vmoptions, the equivalent container property will be stored in <installation_directory>/conf/container.properties when you click Save on the Properties panel. The original system property will be removed from /bin/atom.vmoptions.

Proxy User ID

  • Default Value: Not set
  • Format: String
  • com.boomi.container.proxyUser

The name of the user who can log into the proxy server.

Purge Manager

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.config.runPurgeManager

See the topic about disk space monitoring and the purge manager.

Purge Manager Threads

  • Default Value: Varies
  • Format: Positive integer
  • com.boomi.container.purge.numPurgeThreads

The number of threads to be used for purging runtime logs and data. The value cannot be set to 0. If Purge Manager is run from a basic runtime, runtime cluster, or runtime cloud, the default is 1. If Purge Manager is run from the Runtime Maintenance Server, the default is 10. For more information, see the topic about purging logs and data.

Purge Schedule for Components

  • Default Value: Not set
  • Format: Days
  • com.boomi.container.component.purgeDays

The number of days to wait before purging test execution and browse component data held on your basic runtime, runtime cluster, or private runtime cloud. If not explicitly set in the user interface, the default is set to 0, meaning the property is disabled until a user configures the property with a positive integer, enabling the purge.Shared HTTP Server SSL Certificates and Certificate Authorization components are not purged as a result of enabling this property. See the topic about purging logs and data.

Purge Schedule for Logs

  • Default Value: Not set
  • Format: Days
  • com.boomi.container.logs.PurgeDays

See the topic about purging logs and data.

Purge Schedule for Processed Documents

  • Default Value: Not set
  • Format: Days
  • com.boomi.container.data.PurgeDays

See the topic about purging logs and data.

Purge Schedule for Temporary Data

  • Default Value: Not set
  • Format: Days
  • com.boomi.container.temp.PurgeDays

See the topic about purging logs and data.

Retry HTTP Post

  • Default Value: Off
  • Format: Check box
  • -Dsun.net.http.retryPost

Specifies whether an unsuccessful HTTP POST request should be resent to the server automatically.

Rolling Restart Force Timeout

  • Default Value: 30 minutes
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.cluster.rollingRestart.forceRestartTimeout

The amount of time a node will wait for rolling restart to complete. After this amount of time, the node begins restarting regardless of the status of any other nodes.

Rolling Restart Next in Line Timeout

  • Default Value: 5 minutes
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.cluster.rollingRestart.nextInLineRestartTimeout

The amount of time a node will wait for the "next in line" node to complete the restart process and return to RUNNING status (measured from when the node actually initiates the active restart process).

Security Policy

  • Default Value: Not set
  • Format: String (likely LOW or HIGH)
  • com.boomi.container.forker.securityLevel

See the topic Security policies for Clouds and Molecueles.

Set Local JAR Directory

  • Default Value: Not set
  • Format: Full directory path
  • com.boomi.container.localJarDir

Specifies the local working directory to which JAR files, plugins, connectors, and custom libraries are copied for each node in a cluster when they are updated or downloaded.

note

This functionality is now included as part of the Use Local Storage for Runtime Assets setting on the Properties panel, Basic tab. We recommend not using Set Local JAR Directory and instead use the Use Local Storage for Runtime Assets. However, if you have configured Set Local JAR Directory, that directory will still be used for copied JARs only, regardless of the other local storage configuration.

Sequential Processing of Custom Script Engine Data

  • Default Value: FALSE
  • Format: TRUE or FALSE
  • com.boomi.container.enableBatchProcessScriptEngineData

Reduces memory issues when executing Groovy scripts. When enabled, no more than one document is processed at a time in sequential order. does not recommend enabling this property if you plan to extensively modify the original Groovy script. This property is disabled by default.

note

We do not recommend enabling this property the script is modified with multiple iterations to process documents. If you want to access documents multiple times within the same script, we recommend you disable the property.

Show Runtime Icon in System Tray

  • Default Value: TRUE
  • Format: TRUE or FALSE
  • com.boomi.container.showMonitorOnStartup

Specifies whether an icon should be shown for the runtime in the system tray.

Standard Error Log Level

  • Default Value: WARNING
  • Format: OFF, WARNING, or SEVERE
  • com.boomi.container.logging.std.stdErrLevel

Sets the logging level at which logging outputs to standard error (stderr) instead of standard output (stdout) when the Enable Standard Output and Error Logging property is enabled.

TCP Port for Unicast

  • Default Value: 7800
  • Format: A different port
  • com.boomi.container.cloudlet.tcpPort

See the topic about setting up unicast support.

Threads for Account Initialization

  • Default Value: 50
  • Format: Integer
  • com.boomi.container.maxAccountInitThreadPoolSize

The number of threads to use to initialize accounts upon runtime cloud startup.

Threads for Account Initialization During Starting and Stopping Plugins

  • Default Value: 50
  • Format: Integer
  • com.boomi.container.maxAccountUpdateThreadPoolSize

The number of threads to use to initialize accounts in a runtime cloud during the loading of plug-ins.

Threads for Runtime Scheduling

  • Default Value: 5
  • Format: Integer
  • com.boomi.container.numSyncScheduleThreads

The size of the thread pool that handles scheduled events.If you have a lot of activity and if you are experiencing lower performance, consider increasing this number, provided there are sufficient server resources.

Threads for Runtime to Runtime Messages

  • Default Value: Not set
  • Format: Integer
  • com.boomi.container.cloudlet.numSyncClusterThreads

The size of the thread pool for processing messages from other nodes.If this property is not set manually on the Properties panel, the default value automatically utilized by the runtime is 3 for a runtime cluster or 20 for a runtime cloud. If you have a lot of activity and if you are experiencing lower performance, consider using this property to increase the default numbers, provided there are sufficient server resources.

Threads for Runtime to Platform Messages

  • Default Value: 50
  • Format: Integer
  • com.boomi.container.numMessageSendThreads

The size of the thread pool for sending messages from the runtime to the platform.If you have a lot of activity and if you are experiencing lower performance, consider increasing this number, provided there are sufficient server resources.

Threads for Runtime to Platform Polling

  • Default Value: 10
  • Format: Integer
  • com.boomi.container.numSyncPollThreads

The size of the thread pool for sending messages from the platform to the runtime. This property is for incoming synchronous messages. If you have a lot of activity and if you are experiencing lower performance, consider increasing this number, provided there are sufficient server resources.

Timeout for Escalating Cluster Issue

  • Default Value: 0
  • Format: Milliseconds
  • com.boomi.container.cloudlet.problemEscalationTimeout

See the topic about cluster monitoring. If a value is not manually specified in the property field, the property automatically assumes a default of 0 milliseconds.

Timeout for Queued Executions per Node

  • Default Value: 59,000 (= 59 seconds)
  • Format: Hours, minutes, seconds, milliseconds
  • com.boomi.container.queuedExecutionTimeout

The amount of time that queued executions will wait to run on a given node before they are discarded. This property can be used by basic runtimes and by runtime clusters that do not have forked execution enabled. This property can be used if the Maximum Simultaneous Executions per Node property is enabled.

Timeout for Queued Forked Executions per Node

  • Default Value: 59,000 (= 59 seconds)
  • Format: Milliseconds
  • com.boomi.container.forker.queuedForkedExecutionTimeout

The amount of time queued forked executions wait to run on a given node before they are discarded. This property is used by runtime clouds and by runtime clusters that have forked execution enabled.

Timeout for Unicast Auto-detect

  • Default Value: 30
  • Format: Seconds
  • com.boomi.container.cloudlet.findInitialHostsTimeout

The amount of time a node will wait to detect other hosts when using unicast for cluster communication.See the topic about setting up unicast support.

note

Setting this property to an integer less than or equal to 0 disables the auto-detection of initial hosts.

On this Page